🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.

Description

This change adds support for #import statements to use paths to modules.

Example:

# import A from "require:someModule/schema.graphql"

A simplified form, assuming the module package main points at a schema could be:

# import A from "require:someModule"

This is particularly useful for both published shared types and monorepos that wish to avoid relative paths between packages.

Related: #4721

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

See import-schema.spec.ts test: "require paths"

Test Environment:

• OS:
• @graphql-tools/...:
• NodeJS:

Checklist:

• I have followed the CONTRIBUTING doc and the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests and linter rules pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Further comments

Because jest intercepts require statements, I added a path override to the module mapper to ensure the test is able to run.